Automated Docker CLI Options Update - Review

This PR is a routine automated update produced by the ModularPipelines.OptionsGenerator tool, and the change itself is intentionally minimal — only the GeneratedAt timestamp in AssemblyInfo.Generated.cs is bumped (from 2026-05-10 to 2026-05-17).

What the change does

The single modified line advances the assembly metadata timestamp that records when the Docker options classes were last regenerated:

- [assembly: AssemblyMetadata("ModularPipelines.OptionsGenerator.GeneratedAt", "2026-05-10T03:18:10.7050447Z")]
+ [assembly: AssemblyMetadata("ModularPipelines.OptionsGenerator.GeneratedAt", "2026-05-17T03:19:10.0854018Z")]

No option classes, enum values, service interfaces, or any other generated files were modified. The generator ran against the installed Docker CLI version, found no differences in the help output, and the only artifact is the updated timestamp.

Observations and suggestions

1. Timestamp-only PRs add noise without value.
When the generator detects no actual changes to the CLI surface (no new flags, no modified descriptions, no new sub-commands), creating a PR whose sole change is a timestamp update creates review burden without delivering value. Consider suppressing PR creation — or at minimum auto-merging without review — when the diff consists only of the GeneratedAt metadata change. The auto-merge flag is already set here, which helps, but the PR still occupies CI resources and review queues.

2. No change detection before opening a PR.
A lightweight pre-flight check in the automation workflow could compare the generated output (excluding the GeneratedAt line) against the current tree. If nothing substantively changed, the workflow could skip the PR entirely. For example:

# After generating, check if only the timestamp line changed
git diff --ignore-matching-lines='GeneratedAt' -- 'src/ModularPipelines.Docker/**' | grep -q '.' || exit 0

3. Parallel batch of similar timestamp-only PRs.
This PR was opened alongside at least a dozen other tool-update PRs on the same day (buildah, kustomize, vault, helm, packer, terraform, etc.), all of which appear to contain only timestamp bumps. Batching all no-op regenerations into a single PR (or skipping them altogether) would significantly reduce PR churn.

4. The generator and assembly metadata design are sound.
Recording the tool name and generation timestamp as AssemblyMetadata attributes is a clean, zero-overhead approach that surfaces provenance at runtime without polluting the public API. No concerns there.

Previous review comments

No prior review comments exist on this PR.

Verdict

The change is safe to merge as-is — no functional code was altered. The main improvement opportunity is upstream in the CI workflow: avoid opening (or at least auto-close) PRs whose only diff is the regeneration timestamp.